Wearable device, master device operating with the wearable device, and control method for wearable device

ABSTRACT

Provided is a wearable device that is wearable on a body of a user, the wearable device including a display configured to display a screen; a sensor configured to sense a motion of the user; and a controller configured to control the display based on the sensed motion.

CROSS-REFERENCE TO RELATED APPLICATION

This is a divisional of U.S. application Ser. No. 14/688,431 filed onApr. 16, 2015, which claims priority from Korean Patent Application No.10-2014-0045495, filed on Apr. 16, 2014 in the Korean IntellectualProperty Office, the disclosure of which is incorporated herein byreference in its entirety.

BACKGROUND

1. Field

Methods and apparatuses consistent with one or more exemplaryembodiments relate to a wearable device that is wearable on a body of auser, a master device connected with the wearable device, and a methodof controlling the wearable device.

2. Description of the Related Art

With the development of wired and wireless communication networks, smartdevices, which may be used anywhere and be used at any time by beingconnected to a computer network, such as digital devices having variousshapes and functions have been released.

The smart devices may include, but not limited to, wearable devices thatare wearable or attachable to a part of a body of a user. The wearabledevices of various shapes have been released. In the related art, forthe wearable devices, portability is important, and the wearable devicesneed to be wearable by the user without difficulty. Accordingly, thewearable devices have been developed to be small in size and to be lightin weight.

Applications which may perform various functions are installed in thewearable devices, and wearable devices are connected with a motherterminal or master terminal, which is a separate smart device. In thisarrangement, the wearable devices need to continuously communicate withthe mother terminal, and the wearable devices connected with the motherterminal continuously consume power due to the execution of theinstalled applications and the continuous communication with the motherterminal.

In consideration of the importance of portability of wearable devices,internal batteries should be limited in size and the amount of powerconsumed by the wearable devices should be managed. In other words, inorder to increase usage time of the wearable devices, the capacitancesof internal batteries must be increased, which results in an increase insize and weight of the wearable devices and a decrease in portability.

Accordingly, power consumption of the wearable devices needs to bereduced in order to expand the usage time of the wearable devices whilepreventing an increase in size and weight of the wearable devices.

Therefore, there is a need to develop a wearable device which consumesminimal power and is still convenient to use.

SUMMARY

One or more exemplary embodiments include a wearable device which mayreduce power consumption, a master device connected with the wearabledevice, and a method of controlling the wearable device.

One or more exemplary embodiments include a wearable device whichguarantees user convenience and increases usage time thereof, a masterdevice connected with the wearable device, and a method of controllingthe wearable device.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of the presented exemplary embodiments.

According to an aspect of an exemplary embodiment, there is provided awearable device that is wearable on a body of a user, the wearabledevice including: a display configured to display a screen; a sensorconfigured to sense motion of the user; and a controller configured tocontrol the display to display the screen, based on a result of thesensing by the sensor.

The controller may determine whether the user is looking at the screen,based on the result of the sensing by the sensor. When the controllerdetermines that the user is not looking at the screen, the controllermay control the display such that the display does not display thescreen.

The controller may determine whether the user is looking at the screen,based on the result of the sensing of the sensor. When the controllerdetermines that the user is looking at the screen, the controller maycontrol the display such that the display displays the screen.

The controller may control the display such that the display does notdisplay the screen, when the result of the sensing by the sensorincludes a first motion in which the user raises a wrist sequentiallyfollowed by a second motion in which the user lowers the wrist.

The controller may control the display such that the display displaysthe screen when the first motion is sensed, and may control the displaysuch that the display does not display the screen when the second motionis sensed.

The controller may control the display such that the display does notdisplay the screen, when the result of the sensing by the sensorincludes a first motion in which the user turns a wrist in a firstdirection sequentially followed by a second motion in which the userturns the wrist in a second direction different from the firstdirection.

The controller may control the display such that the display does notdisplay the screen, when the result of the sensing by the sensorindicates that the user is walking.

The controller may control the display such that the display does notdisplay the screen, when the result of the sensing by the sensorindicates that the user is running.

The controller may control the display such that the display does notdisplay the screen, when the result of the sensing by the sensorindicates that the user is not wearing the wearable device.

The wearable device may further include a communicator configured totransfer and receive data to and from a master device.

The controller may transmit a first message to the master device torequest the master device to stop transfer of data to the wearabledevice, when the sensor senses that the user has not moved for a firstamount of time.

The controller may transmit a second message to the master device torequest the master device to restart the transfer of data to thewearable device, when the sensor senses a user motion after thecontroller has transmitted the first message.

The controller may control the display such that the display does notdisplay a notification screen corresponding to data transferred from themaster device, when the sensor senses that the user has not moved for afirst amount of time.

According to an aspect of an exemplary embodiment, there is provided amaster device including: a communicator configured to transfer andreceive data to and from a wearable device; and a controller configuredto stop or re-start data transferring and receiving to and from thewearable device, according to a signal strength of the received data.

The communicator may include a Bluetooth module which performs datacommunication with the wearable device according to the Bluetoothcommunication standards. The controller may stop or re-start datatransferring and receiving to and from the wearable device, based on areceived signal strength indicator (RSSI) obtained by the Bluetoothmodule.

The controller may stop data transferring and receiving to and from thewearable device, if the RSSI is less than a first reference value.

The controller may re-start data transferring and receiving to and fromthe wearable device, if the RSSI is equal to or higher than the firstreference value.

According to an aspect to another exemplary embodiment, there isprovided a method of controlling a wearable device that is wearable on abody of a user including: sensing motion of the user; determiningwhether to display a screen of the wearable device, based on a result ofthe sensing; and displaying the screen of the wearable device based onthe determination.

According to an aspect of another exemplary embodiment, there isprovided a wearable device that is wearable on a body of a user, thewearable device including: a display configured to display a screen; asensor configured to sense motion of the user; and a controllerconfigured to control the display based on the sensed motion.

The controller may be configured to determine whether the user islooking at the screen based on the sensed motion, and in response to thecontroller determining that the user is not looking at the screen, thecontroller may be configured to control the display to not display thescreen.

The controller may be configured to determine whether the user islooking at the screen based on the sensed motion, and in response to thecontroller determining that the user is looking at the screen, thecontroller may be configured to control the display to display thescreen.

The controller may be configured to control the display to not displaythe screen, in response to the sensed motion comprising a first motioncorresponding to the user raising a wrist sequentially followed by asecond motion corresponding to the user lowering the wrist.

The controller may be configured to control the display to display thescreen in response to the sensor sensing the first motion and configuredto control the display to not display the screen in response to thesensor sensing the second motion.

The controller may be configured to control the display to not displaythe screen, in response the sensed motion comprising a first motioncorresponding to the user turning a wrist in a first directionsequentially followed by a second motion corresponding to the userturning the wrist in a second direction different from the firstdirection.

The controller may be configured to control the display not to displaythe screen, in response to the sensed motion indicating that the user iswalking.

The controller may be configured to control the display to not displaythe screen, in response to the sensed motion indicating that the user isrunning.

The controller may be configured to control the display to not displaythe screen, in response to the sensed motion indicating that thewearable device is not provided on the user.

The wearable device may further include a communicator configured totransfer and receive data to and from a master device.

The controller may be configured to transmit a first message to themaster device to request the master device to stop transfer of data tothe wearable device in response to the sensor sensing that the user hasnot moved for a first duration.

The controller may be configured to transmit a second message to themaster device to request the master device to restart the transfer ofdata to the wearable device in response to the sensor sensing a usermotion after the controller transmitting the first message.

The controller may be configured to control the display to not display anotification screen corresponding to data transferred from the masterdevice in response to the sensor sensing that the user has not moved fora first duration.

According to an aspect of another exemplary embodiment, there isprovided a method of controlling a wearable device that is wearable on abody of a user, the method including: sensing motion of the user;determining whether to display a screen on the wearable device based onthe sensed motion; and displaying the screen on the wearable devicebased on the determination.

The determining may include: determining whether the user is looking atthe wearable device based on the sensed motion; and determining not todisplay the screen in response to a determination that the user is notlooking at the wearable device.

The determining may include: determining not to display the screen inresponse to the sensed motion comprising a first motion corresponding tothe user raising a wrist sequentially followed by a second motioncorresponding to the user lowering the wrist.

The determining may include: determining not to display the screen inresponse to the sensed motion indicating that the user is not wearingthe wearable device.

The determining may include determining not to display the screen inresponse to the sensed motion comprising a first motion corresponding tothe user turning a wrist in a first direction sequentially followed by asecond motion corresponding to the user turning the wrist in a seconddirection different from the first direction.

The determining may further include: transmitting a first message to amaster device requesting the master device to stop transfer of data tothe wearable device in response to the sensed motion indicating that theuser has not moved for a first duration; and transmitting a secondmessage to the master device requesting the master device to restart thetransfer of data to the wearable device in response to the sensed motionindicating that the user moves after the first message being transmittedto the master device.

The determining may include determining not to display a notificationscreen corresponding to data transferred from the master device inresponse to the sensed motion indicating that the user has not moved fora first duration.

According to an aspect of another exemplary embodiment, there isprovided a wearable device communicating with a master device andwearable on a body of a user, the wearable device including: a displayconfigured to display a screen; a communicator configured to exchangedata between the wearable device and the master device; a sensorconfigured to sense at least one of motion of the user and signalstrength between the wearable device and the master device; and acontroller configured to control the display based on the sensed motionand configured to control the communicator to exchange the data betweenthe wearable device and the master device based on the sensed signalstrength.

The controller may be configured to control the display to display ornot to display the screen in response to the controller determiningwhether the user is looking at the screen or not.

The controller may be configured to control the communicator to exchangeor not exchange the data in response to the controller determiningwhether the sensed signal strength is greater than or equal to a firstreference value.

In response to the controller determining that the user is not lookingat the screen, the controller may be configured to control the displayto not display the screen.

In response to the controller determining that the user is looking atthe screen, the controller may be configured to control the display todisplay the screen.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and/or other aspects of the disclosure will become apparentand more readily appreciated from the following description of exemplaryembodiments, taken in conjunction with the accompanying drawings inwhich:

FIG. 1 is a view for describing a wearable device and a master device,according to an exemplary embodiment;

FIG. 2 is a block diagram of a wearable device, according to anexemplary embodiment;

FIG. 3 is a block diagram of a wearable device, according to anexemplary embodiment;

FIG. 4 is a view for describing an operation of a wearable device,according to an exemplary embodiment;

FIGS. 5A and 5B are views for describing an operation of a wearabledevice, according to an exemplary embodiment;

FIG. 6 is a block diagram of a master device, according to an exemplaryembodiment;

FIG. 7 is a view for describing an operation of a wearable device,according to an exemplary embodiment;

FIG. 8 is a view for describing an operation of a wearable device and amaster device, according to an exemplary embodiment;

FIG. 9 is a view for describing an operation of a wearable device and amaster device, according to an exemplary embodiment;

FIG. 10 is a view for describing an operation of a wearable device and amaster device, according to an exemplary embodiment; and

FIG. 11 is a flowchart illustrating a method of controlling a wearabledevice, according to an exemplary embodiment.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments, examplesof which are illustrated in the accompanying drawings, wherein likereference numerals refer to like elements throughout. In this regard,the exemplary embodiments may have different forms and should not beconstrued as being limited to the descriptions set forth herein. Also,parts in the drawings unrelated to the detailed description are omittedto ensure clarity of the inventive concept.

Accordingly, the exemplary embodiments are merely described below, byreferring to the figures, to explain aspects of the present description.Expressions such as “at least one of,” when preceding a list ofelements, modify the entire list of elements and do not modify theindividual elements of the list.

The terms used in this specification will be briefly described andembodiments of the present inventive concept will be described indetail.

Most of the terms used herein are general terms that have been widelyused in the technical art to which the present invention pertains.However, some of the terms used herein may be created reflectingintentions of technicians in this art, precedents, or new technologies.Also, some of the terms used herein may be arbitrarily chosen by thepresent applicant. In this case, these terms are defined in detailbelow. Accordingly, the specific terms used herein should be understoodbased on the unique meanings thereof and the whole context of thepresent invention.

When a part “includes” or “comprises” an element, unless there is aparticular description contrary thereto, the part can further includeother elements, not excluding the other elements. The term “unit” in theembodiments of the present invention means a software component orhardware components such as a field-programmable gate array (FPGA) or anapplication-specific integrated circuit (ASIC), and performs a specificfunction. However, the term “unit” is not limited to software orhardware. The “unit” may be formed so as to be in an addressable storagemedium, or may be formed so as to operate one or more processors. Thus,for example, the term “unit” may refer to components such as softwarecomponents, object-oriented software components, class components, andtask components, and may include processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,micro codes, circuits, data, a database, data structures, tables,arrays, or variables. A function provided by the components and “units”may be associated with the smaller number of components and “units,” ormay be divided into additional components and “units.”

FIG. 1 is a view for describing a wearable device 120 and a masterdevice 110 according to an exemplary embodiment.

Referring to FIG. 1, a plurality of smart devices may operate while aconnection is established among the same. Hereinafter, descriptions willbe made by focusing on the case in which two smart devices operate andhave a connection established between the two smart devices. Here, thetwo smart devices are a mother terminal operating as the master device110 and the wearable device 120 operating by being connected with theterminal. Also, the wearable device 120 may operate while beingconnected with the mother terminal, or may operate independently fromthe mother terminal.

Hereinafter, the mother terminal is referred to as “the master device”and the smart device which may operate by being connected with themother terminal is referred to as “the wearable device.” The wearabledevice may operate as a slave device of the master device.

The master device 110 may be an electronic device which may autonomouslyperform a pre-determined application or operation by executing installedapplications for performing pre-determined functions. Such master device110 may be, but not limited to, portable computers, such as notebooks,net books, or tablet personal computers (PCs), portable terminals, suchas smart phones or personal digital assistants (PDAs), and smarttelevisions (TVs).

In addition, the wearable device 120 may be attached to, worn on, orinserted into a human body, and may input and output information. Thewearable device 120 may process information that is input and mayperform operations corresponding thereto by executing installedapplications.

Also, the wearable device 120 may be connected with the master device110 via a network, and may transfer and receive data to and from themaster device 110.

Also, the wearable device 120 may autonomously operate. For example, thewearable device 120 may include applications installed therein, andthus, may autonomously perform operations corresponding thereto.

The wearable device 120 may have various shapes. For example, thewearable device 120 may be a watch, a bracelet, or a wearing glasses.

In FIG. 1, the master device 110 is exemplified as a smart phone, andthe wearable device 120 is exemplified as a smart watch which may beworn on a user's wrist. Hereinafter, inter-operations between the twosmart devices, the master device 110 being exemplified as a smart phoneand the wearable device 120 being exemplified as a smart watch, aredescribed.

The master device 110 has various applications installed therein forperforming various operations corresponding thereto. For example, themaster device 110 may execute applications for reproducing media, suchas music and video, messenger applications for chatting or fortransferring and receiving messages, such as texts, and applications forgames. The master device 110 displays a user interface screen for userinterfacing or an application execution screen via a display 115.

The wearable device 120 may transfer and receive data to and from themaster device 110 through a network. For example, the wearable device120 receives information about various events occurring in the masterdevice 110 and displays a screen for notifying a user of the receivedinformation, via a display 125 of the wearable device 120.

When events such as phone calls, alarms, schedules, unanswered calls,text messages, chat messages, and emails occur in the master device 110,the master device 110 transfers data related to the above-describedevents to the wearable device 120 through a network. Then, the wearabledevice 120 may receive the data transferred from the master device 110and display a screen notifying the user of the occurrence of the eventsvia the display 125.

When a user sets a notification mode of the master device 110 to avibration mode and puts the master device 110 in a pocket of his/hercoat, or when a user sets the notification mode of the master device 110to a sound mode and is in a noisy location, the user may be unable toinstantly recognize the events occurring in the master device 110. Inthe above-described situations, the user may rapidly and easilyrecognize the events occurring in the master device 110, if the wearabledevice 120 outputs a notification with respect to the events occurringin the master device 110, by using at least one of vibration, a sound,and a visually recognizable screen.

Also, the wearable device 120 may be used to conveniently control theoperation of the master device 110. For example, when the master device110 is playing a music file, the wearable device 120 may conveniently beused to, for example, select, play, and pause the music file.

Also, the wearable device 120 may operate independently from the masterdevice 110. For example, the wearable device 120 may include a sensorrelated to fitness, such as a heart rate sensor, and may provide afitness function by using the included sensor. For example, the wearabledevice 120 may measure exercise time and a traveled distance whilerunning, hiking, etc, and may measure a heart rate of the user andprovide the same to the user.

Hereinafter, detailed configurations of wearable devices which mayreduce power consumption, according to exemplary embodiments of thepresent inventive concept, will be described by referring to FIGS. 2through 10.

FIG. 2 is a block diagram of a wearable device 200 according to anexemplary embodiment.

Referring to FIG. 2, the wearable device 200 may include a display 220,a sensor 230, and a controller 240. Also, the wearable device 200 mayfurther include a communicator 250.

The display 220 displays a screen. In detail, the display 220 mayinclude a display panel (not shown) and may display the screen by usingthe display panel. Here, the display panel may be an LCD panel, an OLEDpanel, an AMOLED panel, or a PDP panel.

The sensor 230 senses motion of a user. For example, the sensor 230 maysense motion of a pre-determined body part of the user while the user iswearing the wearable device 200 on the pre-determined body part.

The controller 240 controls whether the screen is displayed based on aresult of the sensing of the sensor 230. For example, the controller 240may control the display to turn the screen on or off based on the resultof the sensing of the sensor 230.

The controller 240 may determine whether the user is looking at thescreen, based on the result of the sensing by the sensor 230. Inresponse, when it is determined that the user is not looking at thescreen, the controller 240 may control the display not to display thescreen. Also, the controller 240 determines whether the user is lookingat the screen, based on the result of the sensing by the sensor 230.When it is determined that the user is looking at the screen, thecontroller 240 may control the display to display the screen.

The controller 240 may access sensing data of the sensor 230, and whenthe sensing data indicates a certain motion of the user, the controller240 may determine that the user is not looking at the display 220 andmay control the display 220 such that the display 220 does not displaythe screen.

Also, the controller 240 may control the display 220 such that thedisplay 220 does not display the screen, when the controller 240determines that the user is not using the wearable device 200, based onthe result of the sensing of the sensor 230.

Hereinafter, displaying of the screen via the display 220 is referred toas “display on” and non-displaying of the screen by shutting off orminimizing power supplied to the display panel is referred to as“display off.” When the display is off, the power supplied to thedisplay panel is shut off or the display panel displays only a blackscreen.

The communicator 250 may transfer and receive data to and from a masterdevice (i.e., See FIG. 1; 110), which is another smart device connectedwith the wearable device 200 via a wired or wireless network.

For example, when the controller 240 determines that the user is notlooking at or using the wearable device 200, based on the result of thesensing of the sensor 230, the controller 240 may control the display220 such that the display 220 does not display a notification screencorresponding to an event even if data indicating an occurrence of theevent (for example, receipt of a text message) is received from themaster device via the communicator 250.

Detailed operations and configurations of the wearable devices will bedescribed hereinafter by referring to FIGS. 3 through 10.

FIG. 3 is a block diagram of a wearable device 300 according to anexemplary embodiment. The wearable device 300 may include a display 320,a sensor 330, and a controller 340. Also, the wearable device 300 mayfurther include at least one selected from a communicator 350, a userinterface 360, a memory 370, and a battery 380. In FIG. 3, the display320, the sensor 330, and the controller 340 respectively correspond tothe display 220, the sensor 230, and the controller 240 illustrated inFIG. 2. Thus, repeated descriptions with respect to FIG. 2 will beomitted in the description of the wearable device 300.

Referring to FIG. 3, the display 320 displays a screen.

For example, the screen displayed by the display 320 may include a watchscreen showing the time, a screen displayed according to execution of anapplication installed in the wearable device 300, a screen indicating anevent occurring in a connected master device (i.e., See FIG. 1; 110), ora screen for controlling the connected master device.

In detail, the event occurring in the connected master device mayinclude receipt of a short message service (SMS) message, a multi-mediamessage service (MMS) message, an email, or a chat-on message, anotification of an occurrence of a schedule according to a schedulemanagement application, or a time notification. When the above-describedevents occur in the master device, the screen indicating the events maybe output via the display 320 of the wearable device 300. Hereinafter,the screen displayed by the display 220 in correspondence with theoccurrence of the above-described events is referred to as anotification screen.

The sensor 330 includes at least one sensor for sensing motion of auser. For example, the sensor 330 may sense user's motion inthree-dimensions (i.e., a gesture of the user).

The sensor 330 may include a sensor 331 which may sense the motion insix (6) directions including up, down, right, left, forward, andbackward. The sensor 330 may also include an accelerometer sensor 332.Also, the sensor 330 may further include a gyroscope sensor 333.

The accelerometer sensor 332 may measure gravitational acceleration andan acceleration of motion with respect to Cartesian axes (i.e., in x, y,and z directions) to measure a velocity and/or location of the wearabledevice 300.

Also, the gyroscope sensor 333 may measure a change in angle bymeasuring an acceleration with respect to the x, y, and z axes, and maymeasure the velocity and/or location of the wearable device 300.

The sensor 330 may sense the motion of the user in the six (6)directions, based on the sensing result via at least one of theaccelerometer sensor 332 and the gyroscope sensor 333.

Also, the sensor 330 may further include at least one of a pedometer 335and a heart rate sensor 336. The pedometer 335 is a sensor for recordingsteps of a user, and may record the movement of the user according tothe number of steps taken by the user. Also, the heart rate sensor 336may measure a heart rate of the user. For example, when the userexercises, or needs to measure heart rate, the user may use the heartrate sensor 336.

Also, the sensor 330 may further include a geomagnetic sensor (notshown), a gravity sensor (not shown), a light sensor (not shown), and atemperature sensor (not shown). The geomagnetic sensor is a sensor thatmay detect an azimuth by using an earth's magnetic field. The gravitysensor is a sensor which detects motion by searching a direction ofgravity, and may recognize alignment of the wearable device 300 withrespect to a vertical direction or a horizontal direction. Also, thetemperature sensor is a sensor which may measure temperature.

The sensor 330 may sense various types of motion including the gestureof the user, by using the above-described sensors.

The communicator 350 transfers and receives data to and from the masterdevice, which is another smart device connected with the wearable device300 via a wired or wireless network. For example, the communicator 350may receive information corresponding to events occurring in the masterdevice. Here, the information corresponding to events may include theSMS message, the MMS message, the email, or the chat-on message. Thecommunicator 350 receives data including the information with respect tothe SMS message, the MMS message, the email, and the chat-on messagefrom the master device. Hereinafter, the data transferred from themaster device to the communicator 350 of the wearable device 300 incorrespondence with the events occurring is referred to as “notificationdata.” Also, the screen generated in correspondence with thenotification data is referred to as a “notification screen.”

The communicator 350 may include a communication module for accessing apre-determined network in a wired or wireless manner. For example, thecommunicator 350 may include a Bluetooth module 311. Bluetooth is acommunication protocol via which electronic devices may communicate withone another and transfer and receive data at high speed by using a radiofrequency signal, without any physical connection (e.g., a cable).Bluetooth consumes little power when transferring and receiving data andmay stably transfer and receive data, and thus, if Bluetooth is used fortransferring and receiving data between the wearable device 300 and themaster device, power consumption may be reduced, while data is stablytransferred and received.

The Bluetooth module 311 may receive the notification data transferredfrom the master device in a serial port profile (SPP) method. Forexample, the Bluetooth module 311 may receive the SMS message, the MMSmessage, the email, or the chat-on message, the notification informationof a schedule occurrence according to the schedule managementapplication, and the time notification information, by using the SPPmethod.

Also, the communicator 350 may be a communication module configured totransfer and receive data to and from the master device via, forexample, a wireless LAN (WLAN), Wi-Fi, 3G, long term evolution (LTE),wireless broadband (Wibro), world interoperability for microwave access(Wimax), CDMA, or WCDMA.

Also, the communicator 350 may be a communication module configured totransfer and receive data to and from the master device via near fieldcommunication (NFC). Accordingly, because NFC is supported, when themaster device is near to or contacts the wearable device 300,pre-determined data may be transferred and received between the masterdevice and the wearable device 300.

Hereinafter, descriptions will be made by focusing on the case in whichthe communicator 350 includes the Bluetooth module 311.

The Bluetooth module 311 may measure strength of a signal transferredfrom the master device, and the controller 340 may control on and off ofa display according to the strength of the received signal measured bythe Bluetooth module 311.

Specifically, the Bluetooth module 311 may obtain a received signalstrength indicator (RSSI) of the signal transferred and received fromthe master device. Here, the RSSI is a value indicating a strength ofthe signal transferred to the Bluetooth module 311. The controller 340may stop or re-start data transferring and receiving to and from themaster device, according to the signal strength of the received data.For example, the controller 340 may stop data transferring and receivingto and from the master device, if the RSSI is less than a firstreference value. Accordingly, the notification data corresponding to theevent occurrence in the master device may not be received, and thenotification screen may not be displayed.

When a distance between the master device and the wearable device 300 isincreased, the strength of the signal received from the master device isdecreased. Thus, if the RSSI is obtained, whether the wearable device300 is far from or near to the master device may be determined.

Here, the first reference value may vary according to specifications ofthe Bluetooth module 311. For example, if the Bluetooth module 311 isable to detect a low-amplitude signal, the first reference value may beset as a low value. For example, the first reference value may be set as−70 dBm. In this case, if the RSSI is less than −70 dBm, the controller340 may determine that the wearable device 300 is far away from themaster device and may stop data transferring and receiving between thewearable device 300 and the master device. Also, if the RSSI is equal toor higher than −70 dBm, the controller 340 may determine that thewearable device 300 is within a pre-determined distance from the masterdevice and may re-start data transferring and receiving between thewearable device 300 and the master device.

The controller 340 may turn the display on or off, based on the resultof the sensing by the sensor 330. For example, the controller 340 maycontrol the display such that the display turns off the screen of thedisplay 320 or such that the display does not display the notificationscreen even when the notification of an event occurrence is receivedfrom the master device, if it is determined that the user is not lookingat the display 320 of the wearable device 300 or that the user is notusing the wearable device 300, based on the result of the sensing of thesensor 330.

Specifically, the controller 340 determines whether the user is movingby accessing sensing data output by the sensor 330. Also, when it isdetermined that the user is not moving, the controller 340 may controlthe screen of the display 320 such that the screen is turned off.

For example, when the user puts the wearable device 300 on a table orwhen the user is asleep while wearing the wearable device 300, thesensor 330 does not sense motion, and, the controller 340 may determinethat the user is not using the wearable device 300. The controller 340may control the display 320 such that the display 320 turns off thescreen of the display 320 when the controller 340 determines via thesensor 330 that the user has not moved for a period of time, forexample, one hour, in order to prevent power consumption which wouldotherwise result if the screen of the display 320 is turned on even whenthe user is not moving. Here, the predetermined period of time may bedirectly input by the user or the controller 340 may autonomously setthe same.

Also, the controller 340 may determine whether the user is wearing thewearable device 300 or not by accessing the sensing data output from thesensor 330. For example, the sensor 330 may sense the motion of the userby using at least one of the gyroscope sensor 333 and the accelerometersensor 332. Alternatively, when the sensor 330 includes a temperaturesensor (not shown), the controller 340 may determine that the user iswearing the wearable device 300, if a temperature corresponding to bodyheat is sensed by the temperature sensor. Alternatively, when the sensor330 includes the heart rate sensor 336, the controller 340 may determinethat the user is wearing the wearable device 300, if the user's heartrate is sensed by the heart rate sensor 336. Also, the controller 340may control the screen of the display 320 such that the screen is notdisplayed, when it is determined that the user is not wearing thewearable device 300.

Also, the controller 340 may detect whether the user raises a wrist orwhether the user turns the wrist by accessing the sensing data outputfrom the sensor 330. Also, the controller 340 may control the display onand off according to whether a gesture that the user raises the wrist issensed or not. The user interface 360 receives an input of a request, aninstruction, or other data from the user.

The user interface 360 may be a touch screen. For example, the userinterface 360 may include a touch pad (not shown) which is combined witha display panel (not shown). When the user interface 360 is a touchscreen, the user interface 360 may output, on the display panel that iscombined with the touch pad, a menu screen that is a user interfacescreen. When the user touches a pre-determined point on the menu screen,for example, a point in which a mirroring service menu is displayed, theuser interface 360 senses the point touched by using the touch pad.Then, the user interface 360 may transfer the sensing information to thecontroller 340. Then, the controller 340 may interpret the touched pointto interpret the user's command and request and the data.

The memory 370 may store at least one selected from various data,programs, applications, and data transferred and received.

The battery 380 includes a rechargeable battery and supplies power toeach component of the wearable device 300.

Hereinafter, an operation for determining whether the user is looking atthe display 320 of the wearable device 300 or not based on the result ofthe sensing of the sensor 330 will be described in detail by referringto FIGS. 4 and 5.

FIG. 4 is a view for describing an operation of the wearable device 300.

Referring to FIGS. 3 and 4, the controller 340 may control the screensuch that the screen is not displayed, when the controller 340 senses afirst motion in which a user raises a wrist 410 sequentially followed bya second motion in which the user lowers a wrist 420, based on theresult of the sensing of the sensor 330.

Specifically, when the user raises the wrist 410 and then lowers thewrist 420 as illustrated in FIG. 4, the screen 421 of the wearabledevice 300 may be turned off. In the case of the wearable device 300worn on a wrist, the user has to raise the wrist 410 as illustrated in atop figure of FIG. 4, when a user wants to view the screen of thewearable device 300. Then, once the user has identified the informationdisplayed by the screen 411, the user may lower the wrist 420 again asillustrated in a bottom figure of FIG. 4. When the wrist 420 is lowered,the user may be unable to view the screen 421, and thus, the screen 421does not need to be displayed. Therefore, when the wrist 410 is raised,the screen 411 of predetermined content is displayed on the screen 411,and when the wrist 420 is lowered, nothing is displayed on the screen421, as indicated by a portion 425 illustrated in FIG. 4.

As described above, the controller 340 may control the display 320 suchthat the display turns off the screen of the display 320, when theuser's wrist is raised and then lowered, so that power consumption maybe reduced.

The sensing operation of the wrist motion may be performed by thecontroller 340 as follows.

The accelerometer sensor 332 of the sensor 330 transfers sensing data tothe controller 340. The controller 340 logs onto the sensing data andsenses motion and recognizes a “no move” point where the motion stops.Then, the controller 340 determines a gesture of the user by using thesensing data at the “no move” point. Specifically, the controller 340may determine whether the user performs an operation of looking at thescreen of the wearable device 300, by using the sensing data at the “nomove” point. The controller 340 may determine that the user is lookingat the screen of the wearable device 300, when the sensing dataindicates that a variation between motion of the user at a point priorto the “no move” point and motion of the user at the “no move” point hasa value of −3 m/s² through 3 m/s² in a direction of an x axis, and thesum of a variation of the sensing data sensed at the “no move” point inan direction of a y axis and a variation of the sensing data sensed atthe “no move” point in a direction of a z axis is equal to or higherthan 5 m/s². A data value of the accelerometer sensor 332, by which thegesure of the user looking at the screen of the wearable device 300 maybe determined, may be obtained experimentally or statistically. That is,an accelerometer variation that is a data value of the accelerometersensor 332 is determined by measuring acceleration and decelerationvalues corresponding to gestures of a plurality of users looking at thescreen of the wearable device 300, and then, based on the measuredacceleration and deceleration values, a reference value for determiningthe gesture of the user looking at the screen of the wearable device 300may be set. Also, the reference value according to the exemplaryembodiment may be changed according to experimental results.

A gesture of the user not looking at the screen of the wearable device300 by lowering the wrist may be determined when a reverse directionvariation of the variation of the sensing data when the wrist is raisedis sensed. Here, forward and backward directions of the user may bealong the x axis, right and left directions of the user may be along they axis, and up and down directions of the user may be along the z axis.

As described above, the accelerometer sensor 332 of the sensor 330measures the variations in measured acceleration and deceleration in thex, y, and z axis directions, and the controller 340 may specificallydetermine the gesture of the user based on the variation measured by theaccelerometer sensor 332.

For example, when notification data notifying an event is received fromthe master device, the controller 340 may control the notificationscreen notifying the event occurrence such that the notification screenis displayed. Accordingly, the display 320 turns on the display anddisplays the notification screen. Then, the user may view thenotification screen by raising the wrist 410. Next, when the user viewsthe notification screen and lowers the wrist 420, the controller 340 maysense the motion of the user and control the display 320 such that thedisplay 320 turns off the display.

Also, when the first motion in which the user's wrist is raised issensed, the controller 340 may control the screen such that the screenis displayed, and when the second motion in which the user's wrist islowered is sensed, the controller 340 may control the screen such thatthe screen is not displayed.

FIG. 5 is a view for describing an operation a wearable device 520according to an exemplary embodiment.

Referring to FIGS. 3 and 5, the controller 340 may control the screensuch that the screen is not displayed, when the controller 340 senses afirst motion in which a user 510 turns a wrist 530 in a first directionsequentially followed by a second motion in which the user turns a wrist550 in a second direction, based on the result of the sensing of thesensor 330.

Referring to FIG. 5A, the user 510 turns/rotates the wrist 530 in thefirst direction and views a screen 525 displayed by the wearable device520.

Next, as illustrated in FIG. 5B, the user 510 identifies the screen 525,and then turns the wrist 550 in the second direction that is opposite tothe first direction. When the wrist 550 is turned in the seconddirection, the controller 340 may control a screen of a wearable device540 such that the display of the screen is turned off.

In the case of the wearable device 510 worn on a wrist, the user needsto turn the wrist 530 towards the user so that the screen 525 faces theuser's face as illustrated in FIG. 5A in order to view the screen 525 ofthe wearable device 510. Then, after the user views the informationdisplayed by the screen 525, the user may return the wrist 530 back toits original position. Thus, if the screen of the wearable device 540does not face the face of the user 510 since the wrist 550 is returnedto the original position thereof, as illustrated in FIG. 5B, the usermay be unable to view the screen of the wearable device 540 such thatthere is no need to turn on the display of the screen.

As described above, the controller 340 may control the display 320 suchthat the display 320 turns off the display of the screen, when theuser's wrist is turned in the first direction and then subsequentlyturned again in the second direction that is opposite to the firstdirection, thereby reducing power consumption.

When an event occurs in the master device and data notifying the eventis received from the master device, the controller 340 may control thenotification screen notifying the occurrence of the event such that thenotification screen is displayed. Accordingly, the display 320 may turnon the display and display the notification screen. Then, the user mayview the notification screen by turning the wrist 530 in the firstdirection. Next, when the user turns the wrist 550 in the seconddirection opposite to the first direction after viewing the notificationscreen, the controller 340 may sense the motion of the user via thesensor 330 and may control the display 320 such that the display 320turns off the display of the screen.

Also, when the controller 340 senses that the user is running based onthe result of the sensing of the sensor 330, the controller 340 maycontrol the screen such that the screen is not displayed. For example,the sensor 330 may sense that the user is running, by using anaccelerometer value corresponding to forward and backward directions inwhich the user is running as sensed by the accelerometer sensor 333 anda heart rate value of the user sensed by the heart rate sensor 336. Whenthe user is exercising, the user may not be aware of a notification dueto an event occurrence in the master device even if the notification istransferred to the display 320 from the master device. Thus, in thiscase, the display 320 may control the display 320 to not display thenotification screen, in order to reduce power consumption.

Also, when the controller 340 senses that the user is walking based onthe result of the sensing of the sensor 330, the controller 340 maycontrol the screen such that the screen is not displayed. For example,the sensor 330 may sense that the user is walking, by using anaccelerometer value corresponding to forward and backward directions inwhich the user is walking as sensed by the accelerometer sensor 333 andthe number of steps taken by the user as sensed by the pedometer 335.When the user is walking, the user may not be aware a notification dueto an event occurrence in the master device even if the notification istransferred to the display 320 from the master device. Thus, in thiscase, the display 320 may not display the notification screen, in orderto reduce power consumption.

FIG. 6 is a block diagram of a master device 600 according to anexemplary embodiment.

The master device 600 is a smart device which may operate by beingconnected with the wearable device 300, and corresponds to the masterdevice 110 described with reference to FIG. 1. Thus, repeateddescriptions with respect to FIG. 1 will be omitted in the descriptionof the master device 600.

The master device 600 may be an electronic device which may autonomouslyperform a pre-determined application or operation executing applicationsinstalled therein for performing pre-determined functions, such asportable computers, such as notebooks, net books, or tablet PCs,portable terminals, such as smart phones or PDAs, and smart TVs.Hereinafter, the case in which the master device 600 is a smart phonewhich may operate by being connected with the wearable device 300 willbe described.

Referring to FIG. 6, the master device 600 includes a communicator 610and a controller 620. Also, the master device 600 may further include adisplay 630, a user interface 640, a battery 650, and a memory 660.

The communicator 610 transfers and receives data to and from thewearable device 300.

The communicator 610 transfers and receives data to and from thewearable device 300, which is another smart device connected with themaster device 600 via a wired or wireless network. For example, thecommunicator 610 may transfer notification data for notifying a user ofan occurrence of an event when the event such as receipt of an email, atext message, and a chat-on message occurs, to the communicator 350 ofthe wearable device 300. Also, the communicator 610 may transfer andreceive pre-determined data to and from an external electronic device ora server through a pre-determined network. The communicator 610 mayinclude a communication module for accessing the pre-determined networkin a wired or wireless manner. For example, the communicator 610 mayinclude a Bluetooth module 615 which transfers and receives dataaccording to the Bluetooth communication standards.

Also, the communicator 610 may include a WLAN, Wi-Fi, 3G, LTE, Wibro,Wimax, CDMA, or WCDMA module to transfer and receive data to and fromother electronic devices including the wearable device 300.

Also, the communicator 610 may include a communication module accordingto NFC. Accordingly, since a near field connection method is supported,when other electronic devices including the wearable device 300 is nearor contacts the master device 600, pre-determined data may betransferred and received between the electronic devices and the masterdevice 600.

Hereinafter, descriptions will be made by focusing on the case in whichthe communicator 610 includes the Bluetooth module 615, and the masterdevice 600 transfers and receives data to and from the wearable device300 by using the Bluetooth module 615. The Bluetooth module 615 maymeasure strength of a signal transferred from the wearable device 300.In detail, the Bluetooth module 615 may obtain an RSSI of the signaltransferred and received from the wearable device 300.

The controller 620 may stop or re-start data transferring and receivingto and from the wearable device 300 according to the strength of thetransferred or received signal.

The controller 620 may stop or re-start data transferring and receivingto and from the wearable device 300 based on the RSSI obtained from theBluetooth module 615. In detail, the controller 620 may stop datatransferring and receiving to and from the wearable device 300, if theRSSI is less than a first reference value. When a distance between themaster device 600 and the wearable device 300 is increased, the strengthof the signal received by the Bluetooth module 615 of the master device600 is decreased. Thus, if the RSSI is obtained, whether the wearabledevice 300 is far from or near to the master device 600 may bedetermined.

Here, the first reference value may vary according to specifications ofthe Bluetooth module 615. For example, if the Bluetooth module 615 isable to detect a low-amplitude signal, the first reference value may beset as a low value. For example, the first reference value may be set as−70 dBm. In this case, if the RSSI is less than −70 dBm, the controller620 may determine that the wearable device 300 is far away from themaster device 600 and may stop data transferring and receiving betweenthe wearable device 300 and the master device 600. Also, if the RSSI isequal to or higher than −70 dBm, the controller 620 may determine thatthe wearable device 300 is within a pre-determined distance from themaster device 600 and may re-start data transferring and receivingbetween the wearable device 300 and the master device 600.

The display 630 may display a screen. Here, the screen may include ascreen displayed according to an execution of an application installedin the master device 600, a menu screen, a user interface screen, or ascreen corresponding to an event occurrence.

The user interface 640 receives an input of a request, an instruction,or other data from a user.

The user interface 640 may be a touch screen. For example, the userinterface 640 may include a touch pad (not shown) which is combined witha display panel (not shown). When the user interface unit 640 is thetouch screen, the user interface unit 640 may output, on the displaypanel that is combined with the touch pad, a menu screen that is a userinterface screen. When the user touches a pre-determined point on themenu screen, for example, a point in which a mirroring service menu isdisplayed, the user interface 640 senses the touched point. Then, theuser interface 640 may transfer the sensing information to thecontroller 620. The battery 650 includes a rechargeable battery andsupplies power to each component of the master device 600.

The memory 660 may store various data, programs needed for operations ofthe master device 600, applications, and data transferred and received.

FIG. 7 is a view for describing an operation of a wearable device 720according to an exemplary embodiment. A master device 710 and thewearable device 720 illustrated in FIG. 7 respectively correspond to themaster device 600 and the wearable device 300, and thus, repeateddescriptions with respect to FIGS. 3 and 6 will be omitted.

Referring to FIG. 7, the master device 710 may stop or re-start datatransferring and receiving according to a distance between the masterdevice 710 and the wearable device 720. For example, when the distancebetween the wearable device 720 and the master device 710 is equal toless than a first reference distance Dref, the master device 710 maycontinue data transferring, and when the distance between the wearabledevice 720 and the master device 710 is higher than the first referencevalue Dref, the master device 710 may discontinue the data transferring.Also, when the data transferring is discontinued, the master device 710may re-start the data transferring if the distance between the wearabledevice 720 and the master device 710 is equal to or lower than the firstreference distance Dref. For example, if the wearable device 720 islocated at a point P1 which is apart from the master device 710 by afirst distance D1, the master device 710 may retain data transferring tothe wearable device 720. Also, if the wearable device 720 is located ata point P2 which is apart from the master device 710 by a seconddistance D2, the master device 710 may retain data transferring to thewearable device 720. Here, the distance between the master device 710and the wearable device 720 may be measured based on the RSSI, and thefirst reference distance Dref may be a distance corresponding to thefirst reference value −70 dBm.

FIG. 8 is a view for describing operations of a wearable device 810 anda master device 830 according to an exemplary embodiment. In FIG. 8, thewearable device 810 and the master device 830 correspond to the wearabledevice 300 and the master device 600, and thus, repeated descriptionswith respect to FIGS. 3 and 6 will be omitted. Also, hereinafter,components of the wearable device 810 will be described by referring tothe components of the wearable device 300 of FIG. 3, and components ofthe master device 820 will be described by referring to the componentsof the wearable device 600 of FIG. 6.

Referring to FIG. 8, the sensor 330 of the wearable device 810 sensesmotion and transfers the sensing data that is a result of the sensing tothe controller 340.

The controller 340 of the wearable device 810 may control a firstmessage requesting a stop of data transferring such that the firstmessage is transmitted to the master device 820, when motion of a useris not sensed for a predetermined duration (e.g., one hour).

Referring to FIG. 8, the sensor 330 of the wearable device 810 sensesthe motion of the user in operation S80. The controller 340 receives thesensing result and logs the sensing result. When the motion of the useris not sensed for the predetermined duration (e.g., one hour), thecontroller 340 transmits the first message requesting the stop of datatransferring to the master device 820 in operation S82.

Accordingly, the communicator 610 of the master device 820 receives thefirst message and transfers the first message to the controller 620. Thecontroller 620 stops the data transferring to the wearable device 810 inoperation S84. For example, if the first message is received, the masterdevice 820 does not transfer notification data notifying an eventoccurrence to the wearable device 810, even when the event such asreceipt of an email, a text message, or a chat-on message occurs in themaster device 820.

If the motion of the user is sensed via the sensor 330 of the wearabledevice 810, the controller 620 transmits a second message requesting are-start of data transferring to the master device 820 in operation S86.

When the second message is received, the master device 820 may transferthe notification data which is not transferred to the wearable device810 due to the stop of data transferring S84 to the wearable device 810in operation S87. When the notification data is received in operationS87, the wearable device 810 may display a notification screencorresponding to the notification data.

Also, when a new event occurs in the master device 820 in operation S88,the communicator 610 of the master device 820 transfers notificationdata corresponding to the new event to the wearable device 810 inoperation S89. Also, when the notification data is received in operationS89, the wearable device 810 displays a notification screencorresponding to the received notification data.

When the user is not using the wearable device 810, (e.g., when the useris not wearing the wearable device 810 or is asleep), the user may notview the notification even if the display 320 displays the notificationscreen. Thus, when the motion of the user is not sensed because the useris not using the wearable device 810 as described above, the wearabledevice 810 may stop the data transferring and receiving and maintain adisplay-off state thereby reducing power consumption due to datatransferring and receiving and displaying of the notification screen.

FIG. 9 is a view for describing operations of a wearable device 910 anda master device 920 according to an exemplary embodiment. In FIG. 9, thewearable device 910 and the master device 920 respectively correspond tothe wearable device 300 and the master device 600, and thus, repeateddescriptions with respect to FIGS. 3 and 6 will be omitted. Also,hereinafter, components of the wearable device 910 will be described byreferring to the components of the wearable device 300 of FIG. 3, andcomponents of the master device 920 will be described by referring tothe components of the master device 600 of FIG. 6.

Referring to FIG. 9, the sensor 330 of the wearable device 910 sensesmotion of a user in operation S91.

When it is determined that there is no motion of the user, based on aresult of the sensing of the sensor 330, the controller 340 of thewearable device 910 controls the display 320 such that the display 320turns off a display in operation S92.

When the display of the wearable device 910 is turned off in operationS92, a notification screen corresponding to an event is not displayed,even when the event occurs in the master device 920. In detail, when afirst event occurs in the master device 920, the communicator 350 of themaster device 920 transfers first notification data notifying theoccurrence of the first event to the communicator 350 of the wearabledevice 910 in operation S94. However, because the wearable device 910maintains the display-off state S92, the wearable device 910 does notdisplay a notification screen corresponding to the first notificationdata, even when the first notification data is received. Also, thememory 370 of the wearable device 910 may store the first notificationdata.

Thereafter, when the motion of the user is sensed, as a result of thesensing of the sensor 330 of the wearable device 910, in operation S95,the display 320 displays a screen in operation S96. That is, when themotion of the user occurs in operation S95, the display 320 is convertedfrom the display-off state to a display-on state.

When the motion of the user occurs in operation S95, the controller 340controls the display 320 such that the display 320 displays thenotification screen corresponding to the first notification data that ispreviously received and stored in the memory 370, in operation S96.

Also, when a second event that is a new event occurs in the masterdevice 920, in operation S97, the communicator 610 of the master device920 transfers second notification data corresponding to the second eventto the wearable device 910 in operation S89. Because the wearable device910 maintains the display-on state, the display 320 of the wearabledevice 910 displays a notification screen corresponding to the secondnotification data, in operation S99.

When the user is not using the wearable device 910, such as when theuser is not wearing the wearable device 910 or is asleep, the user maynot view the notification, even if the display 320 displays thenotification screen. Thus, when the motion of the user is not sensedsince the user is not using the wearable device 910 as described above,the wearable device 910 may maintain the display-off state, in order toreduce power consumption generated by displaying of the notificationscreen.

FIG. 10 is a view for describing operations of a wearable device 1020and a master device 1010 according to an exemplary embodiment. In FIG.10, the wearable device 1020 and the master device 1010 respectivelycorrespond to the wearable device 300 and the master device 600, andthus, repeated descriptions with respect to FIGS. 3 and 6 will beomitted.

The controller 620 of the master device 1010 may stop data transferringto the wearable device 1020, when the RSSI is less than a firstreference value.

Referring to FIG. 10, the master device 1010 and the wearable device1020 maintain a connected state in operation S101. The Bluetooth module615 of the master device 1010 measures a strength of a signal receivedfrom the wearable device 1020, in operation S102. The Bluetooth module615 of the master device 1010 may monitor the strength of the signalperiodically received from the wearable device 1020 in a pre-determinedtime interval. Alternatively, the Bluetooth module 615 of the masterdevice 1010 may measure a signal strength of received data whenever datais received from the wearable device 1020.

If the RSSI of the data received from the wearable device 1020 is lessthan the first reference value, the controller 620 may stop datatransferring to the wearable device in operation S103. Here, the firstreference value may vary according to specifications of the Bluetoothmodule 615.

Next, if the RSSI is equal to or higher than the first reference value,as a result of the measuring of the signal strength in operation S102,the controller 620 of the master device 1010 may re-start datatransferring to the wearable device 1020. Accordingly, when an eventoccurs in the master device 1010, the communicator 610 of the masterdevice 1010 transfers notification data corresponding to the event tothe wearable device 1020 in operation S104.

FIG. 11 is a flowchart illustrating a method 1100 of controlling awearable device, according to an exemplary embodiment. The method 1100may be executed by using the wearable devices (for example, the wearabledevice 300) according to the exemplary embodiments of the inventiveconcept. Also, the method 1100 includes the same operations as theoperations of the wearable devices (for example, the wearable device300) according to the exemplary embodiments, and thus, repeateddescriptions with respect to the wearable devices (for example, thewearable device 300) according to the exemplary embodiments will beomitted. Also, the method 1100 will be described with reference to thewearable device 300 of FIG. 3.

Referring to FIG. 11, the method 1100 includes sensing motion of a uservia the wearable device 300 that is wearable on a body of the user, inoperation S1110. The operation of S1110 may be performed by the sensor330 of the wearable device 300.

Based on a result of the sensing of the motion in operation S1110,whether or not to display a screen of the wearable device 300 isdetermined in operation S1120. The operation S1120 may be performed bythe controller 340 of the wearable device 300. The controller 340 of thewearable device 300 may determine whether the user is looking at thescreen, based on the result of the sensing of the motion via the sensor330, and when it is determined that the user is not looking at thescreen, may determine not to display the screen.

Also, the screen of the wearable device 300 is displayed in operationS1130 according to the determination of the operation S1120. Theoperation S1130 may be performed by the display 320 according to acontrol of the controller 340 of the wearable device 300. The operationS1130 includes turning off a display via the display 320 and notdisplaying the screen, when it is determined not to display the screenin operation S1120. Also, the operation S1130 includes turning on thedisplay via the display 320 and displaying the screen, when it isdetermined to display the screen.

As described above, according to the o above exemplary embodiments, theon and off state of the display of the wearable device may be controlledaccording to the motion of the user, and thus, power consumption of thewearable device may be reduced. Also, by reducing the power consumption,usage time of the wearable device may be increased without increasing abattery capacitance.

One or more programs including commands for performing a method ofcontrolling a screen editing of a display according to the one or moreexemplary embodiments of the present invention may be embodied ascomputer-readable codes on a computer-readable recording medium. Thecomputer-readable recording medium includes any storage device that maystore data which may be read by a computer system. Examples of thecomputer-readable recording medium include read-only memories (ROMs),random-access memories (RAMs), CD-ROMs, magnetic tapes, floppy disks,and optical data storage devices. The computer-readable recording mediummay be distributed over network-coupled computer systems so that thecomputer-readable codes are stored and executed in a distributedfashion.

It should be understood that the exemplary embodiments described hereinshould be considered in a descriptive sense only and not for purposes oflimitation. Descriptions of features or aspects within each exemplaryembodiment should typically be considered as available for other similarfeatures or aspects in other exemplary embodiments.

While exemplary embodiments have been particularly shown in describedabove, it will be understood by those of ordinary skill in the art thatvarious changes in form and details may be made herein without departingfrom the spirit and scope of the inventive concept as defined by thefollowing claims.

What is claimed is:
 1. A wearable device that is wearable on a body of auser, the wearable device comprising: a display configured to display ascreen; a communicator configured to transfer and receive data to andfrom a master device; a sensor configured to sense a motion of the user;and a controller configured to: obtain sensing data at a motionlesspoint corresponding to a first point when the motion of the user stops,by determining a first variation of acceleration between the motion ofthe user at a second point prior to the motionless point and the motionof the user at the motionless point in a forward-rear direction of theuser and by determining a sum of a second variation of acceleration atthe motionless point in a left-right direction of the user and a thirdvariation of acceleration at the motionless point in an up-downdirection of the user, determine whether the user is looking at thescreen using the sensing data at the motionless point, control thedisplay based on the sensed motion, wherein the controller is furtherconfigured to transmit a first message to the master device to requestthe master device to stop transfer of the data to the wearable devicebased on the sensor sensing that the user has not moved for a firstduration.
 2. The wearable device of claim 1, wherein the sensing data atthe motionless point for determining that the user is looking at thescreen of the wearable device is determined based on an accelerationvariation value from the second point prior to the motionless point tothe motionless point by using at least one acceleration variationregarding at least one direction.
 3. The wearable device of claim 1,wherein the controller is configured to transmit a second message to themaster device to request the master device to restart the transfer ofthe data to the wearable device based on the sensor sensing a usermotion after the controller transmitting the first message.
 4. Thewearable device of claim 1, wherein the controller is configured tocontrol the display to not display a notification screen correspondingto the data transferred from the master device based on the sensorsensing that the user has not moved for the first duration.
 5. Thewearable device of claim 1, wherein: the controller is configured todetermine whether the user is looking at the screen based on the sensedmotion, and based on the controller determining that the user is notlooking at the screen, the controller is configured to control thedisplay to not display the screen.
 6. The wearable device of claim 1,wherein: the controller is configured to determine whether the user islooking at the screen based on the sensed motion, and based on thecontroller determining that the user is looking at the screen, thecontroller is configured to control the display to display the screen.7. The wearable device of claim 1, wherein the controller is configuredto control the display to not display the screen, based on the sensedmotion comprising a first motion corresponding to the user raising awrist sequentially followed by a second motion corresponding to the userlowering the wrist.
 8. The wearable device of claim 7, wherein thecontroller is configured to control the display to display the screenbased on the sensor sensing the first motion and configured to controlthe display to not display the screen based on the sensor sensing thesecond motion.
 9. The wearable device of claim 1, wherein the controlleris configured to control the display to not display the screen, inresponse the sensed motion comprising a first motion corresponding tothe user turning a wrist in a first direction sequentially followed by asecond motion corresponding to the user turning the wrist in a seconddirection different from the first direction.
 10. The wearable device ofclaim 1, wherein the controller is configured to control the display notto display the screen, based on the sensed motion indicating that theuser is walking.
 11. The wearable device of claim 1, wherein thecontroller is configured to control the display to not display thescreen, based on the sensed motion indicating that the user is running.12. The wearable device of claim 1, wherein the controller is configuredto control the display to not display the screen, based on the sensedmotion indicating that the wearable device is not provided on the user.13. The wearable device of claim 1, wherein the controller is configuredto determine that the user is looking at the screen based on the firstvariation of acceleration being in a range between −3 m/s2 and 3 m/s2.14. The wearable device of claim 13, wherein the controller isconfigured to determine that the user is looking at the screen based onthe sum being greater than or equal to 5 m/s2.
 15. The wearable devicemethod of claim 14, wherein the determining further comprisesdetermining that the user is looking at the screen based on the sumbeing greater than or equal to 5 m/s2.
 16. A method of controlling awearable device that is wearable on a body of a user, the methodcomprising: communicating with a master device to transfer and receivedata; sensing a motion of the user; obtaining sensing data at amotionless point by determining a first variation of accelerationbetween the motion of the user at a second point prior to the motionlesspoint and the motion of the user at the motionless point in aforward-rear direction of the user and by determining a sum of a secondvariation of acceleration at the motionless point in a left-rightdirection of the user and a third variation of acceleration at themotionless point in an up-down direction of the user; determiningwhether the user is looking at a screen of the wearable device by usingthe sensing data at the motionless point corresponding to a first pointwhere the motion of the user stops; and displaying the screen on thewearable device based on the determination, transmitting a first messageto the master device to request the master device to stop transfer ofthe data to the wearable device based on sensing that the user has notmoved for a first duration.
 17. The method of claim 16, wherein thesensing data at the motionless point for determining that the user islooking at the screen of the wearable device is determined based on anacceleration variation value from the second point prior to themotionless point to the motionless point by using at least oneacceleration variation regarding at least one direction.
 18. Anon-transitory computer-readable storage medium having a program storedthereon for executing a method comprising: communicating with a masterdevice to transfer and receive data; sensing a motion of a user;obtaining sensing data at a motionless point by determining a firstvariation of acceleration between the motion of the user at a secondpoint prior to the motionless point and the motion of the user at themotionless point in a forward-rear direction of the user and bydetermining a sum of a second variation of acceleration at themotionless point in a left-right direction of the user and a thirdvariation of acceleration at the motionless point in an up-downdirection of the user; determining whether the user is looking at ascreen of a wearable device, by using the sensing data at the motionlesspoint corresponding to a first point where the motion of the user stops;and displaying the screen on the wearable device based on thedetermination, transmitting a first message to the master device torequest the master device to stop transfer of the data to the wearabledevice based on sensing that the user has not moved for a firstduration.